This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
From 5.0.2 release notes ~Joseph Rejipychekoden 12.Jan.04 05:53 PM a Web browser Domino Administrator All ReleasesWindows 2003
I tried the 'platform time 5' & 'platform reset' commands suggested below too. Nothing as yet....
Server
Performance Monitoring Statistics (NT Intel and Solaris Sparc only)
Domino will track performance metrics of the operating system and output the results to the server. Type "show stats platform" at the server console to display them. This feature is disabled by default in R5.0.2. You can enable it by setting the parameter:
PLATFORM_STATISTICS_ENABLED=1
...in the NOTES.INI file and restarting your server. On Windows NT, the following registry setting:
...must be set to NNOTES.DLL in your executable directory. Otherwise performance monitoring will not run. Also on Windows NT, diskperf needs to be enabled for disk metrics to be captured.
Metrics are collected continuously, unless disabled or reset (see commands below), or unless the server is brought down. The server resets this information each time it is started. This feature also expects certain Notes processes to be present. Performance counters for absent Notes processes will have zero values. This is normal behavior.
The server monitors the following metrics:
Performance Metric Description
Platform.Memory.KBFree The amount in kilobytes of virtual memory available on the system. This is equivalent to Memory/AvailableBytes in Windows NT Performance Monitor divided by 1024.
Platform.Memory.PagesPerSec The number of pages read to or written from the disk. Equivalent to Memory/Pages/second in NT Perfmon.
Platform.System.TotalUtil The average percent CPU utilization of all CPU's on the system. Equivalent to System/% Total Processor Time in NT Perfmon.
Platform.System.TotalPrivUtil The average percent CPU utilization in privileged mode of all CPU's on the system. Equivalent to System/% Total Privileged Time in NT Perfmon.
Platform.System.TotalUserUtil The average percent CPU utilization in user mode of all CPU's on the system. Equivalent to System/% Total User Time in NT Perfmon.
Platform.LogicalDisk._Total.1._Total.1.PctTime The percentage of the sampling interval that all logical disks on all physical disks are servicing read or write requests. Equivalent to LogicalDisk/% Disk Time in NT Perfmon. As in NT Perfmon, the first "_Total" refers to all physical disks, and the second "_Total" refers to all logical disks.
Platform.LogicalDisk._Total.1._Total.1.AvgQueueLength (NT only) The average number of both read and write requests that were queued for all logical disks on all physical disks during the sample interval. Equivalent to LogicalDisk/Avg. Disk Queue Length in NT Perfmon.
Platform.LogicalDisk._Total.1._Total.1.ServiceTime (Solaris only) The amount of time in milliseconds for a read or write command to complete.
Platform.Process.nserver.1.Util (NT only) The CPU utilization of the first server process. This is the percentage of the sample interval that the process used the CPU. Equivalent to Process/% Processor Time in NT Perfmon.
Platform.Process.nrouter.1.Util (NT only) The CPU utilization of the first router process.
Platform.Process.nreplica.1.Util (NT only) The CPU utilization of the first replica process.
Platform.Process.nreplica.2.Util (NT only) The CPU utilization of the second replica process.
Platform.Process.nreplica.3.Util (NT only) The CPU utilization of the third replica process.
Platform.Process.nreplica.4.Util (NT only) The CPU utilization of the fourth replica process.
Platform.Process.nupdate.1.Util (NT only) The CPU utilization of the first update process.
Platform.Process.nupdate.2.Util (NT only) The CPU utilization of the second update process.
Platform.Process.nupdate.3.Util (NT only) The CPU utilization of the third update process.
Platform.Process.nupdate.4.Util (NT only) The CPU utilization of the fourth update process.
Platform.Process.nadminp.1.Util (NT only) The CPU utilization of the first adminp process.
Platform.Process.nadminp.2.Util (NT only) The CPU utilization of the second adminp process.
Platform.Process.nadminp.3.Util (NT only) The CPU utilization of the third adminp process.
Platform.Process.nadminp.4.Util (NT only) The CPU utilization of the fourth adminp process.
Platform.Process.nhttp.1.Util (NT only) The CPU utilization of the first http process.
For non-process metrics (those not starting with "Platform.Process"), average, minimum, and maximum statistics are also reported. For example, in addition to Platform.Memory.KBFree, there are the following secondary statistics:
Platform.Memory.KBFree.avg The average of all KBFree samplings for a session. This is calculated by summing all the KBFree samplings, and dividing by the number of samplings.
Platform.Memory.KBFree.min The smallest KBFree sampling for a session
Platform.Memory.KBFree.max The largest KBFree sampling for a session
If a process is removed, the metric for that process will go to 0.
The PLATFORM command allows you to control this feature at the console. It has the following form:
PLATFORM <main argument>
These are the main arguments:
Argument(s) Description
TIME With an optional argument, changes the sampling rate to the specified value in minutes. Otherwise displays the current sampling rate. The default is 1 minute.
RESET Initiates the beginning of a new statistics monitoring session; resets secondary metrics.
WAIT Pauses the collection of performance data
RUN Resumes the collection of performance data
For example, to start a new performance data monitoring session with a sampling rate of 5 minutes, type the following commands at the console:
platform time 5 - The server collects performance data every 5 minutes.
platform reset - Statistic values sampled before this command was issued are not used in calculating average, maximum, or minimum.
Changes have also been made to the Stats and Events database so these statistics can be treated like any other stat (i.e. thresholds, etc. They can be viewed through the Admin client.
Return to top
. . . . . . . . . . . . From 5.0.2 release notes (~Joseph Rejipyc... 12.Jan.04)
Print this page
